pipelines-schema.json is missing configuration for oidc

[Johan Dewe (PostNord)]

There’s no definition for oidc in https://bitbucket.org/atlassianlabs/atlascode/src/main/resources/schemas/pipelines-schema.json

The following snippet gives a warning that “Property oidc is not allowed”.

- step:
    oidc: true
    script:
      - ...

‌

[Oscar Craviotto]

The schema also requires ["access-key", "secret-key"], when pulling awsImage from ECR, but now it is possible to use oidc-role (needs to be added to the schema) in which case key and secret are not required.

[Johan Forssell]

https://bitbucket.org/atlassianlabs/atlascode/issues/66/yaml-validator-inconsistent-with-online

Please help, nothing is happening

[Tom Buico]

Issues like this is why I do not recommend my clients to use Atlassian products.

[Alex Clare]

Thank you.

[Jarrod Moldrich]

Still an issue

[Scott Chamberlain]

This issue is looking forward to it’s 2nd birthday.

[Manoj Acharya]

Still expecting the access key and secret key, even though the documentation says we can use oidc without keys. https://support.atlassian.com/bitbucket-cloud/docs/use-aws-ecr-images-in-pipelines-with-openid-connect/

[Clayton Olney]

Two years later, still an issue.

[Jarrod Lowe]

It also needs to allow:

image:
  name: 0123456789012.dkr.ecr.my-region-1.amazonaws.com/my-ecr-name:latest
  aws:
    oidc-role: $AWS_OIDC_ROLE_ARN

‌

There is even a PR already! https://bitbucket.org/atlassianlabs/atlascode/pull-requests/1025

‌

[Clayton Olney]

Even an acknowledgement would be nice at this point.