We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey team! Nice tool
We are trying to use in our projects, but we got some issues when the executor is defined in an orb.
For example:
build: parameters: environment_env: type: steps default: [] executor: gcp-gcr/default environment: GOOGLE_COMPUTE_ZONE: us-central1-a AWS_DEFAULT_REGION: us-east-1 DOCKER_BUILDKIT: 1
You can't check, but when the compiled version is showed:
build: machine: image: ubuntu-2004:202201-02 environment: - GOOGLE_COMPUTE_ZONE: us-central1-a - AWS_DEFAULT_REGION: us-east-1 - DOCKER_BUILDKIT: 1
I understand it is very difficult to handle all orbs, but maybe we can put a path to open an issue in the repository?
I don't know if we have a simple way to get the compiled YAML too, but I can try to look to send a PR for that
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey team! Nice tool
We are trying to use in our projects, but we got some issues when the executor is defined in an orb.
For example:
You can't check, but when the compiled version is showed:
I understand it is very difficult to handle all orbs, but maybe we can put a path to open an issue in the repository?
I don't know if we have a simple way to get the compiled YAML too, but I can try to look to send a PR for that
The text was updated successfully, but these errors were encountered: