Repository navigation
Conversation
…s not deployed yet Default to the region of the config file and to the team's only AWS account, and fail with a clear error under --no-interaction when a value cannot be resolved. The AWS accounts are now filtered on the team.
…ployed environment
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
bref secret:createon an environment that isn't deployed yet asked for the AWS account and region with prompts, so it failed with--no-interaction(CI, agents), on the path the docs recommend: createAPP_KEY, then deploy.--aws-account(name of the AWS account in Bref Cloud) and--regionoptions, only used when the environment isn't deployed yetprovider.regionin serverless.yml), the AWS account to the team's only accountNo Cloud change needed:
POST /api/v1/secretsalready takesaws_account_idandregion.Docs: brefphp/bref#2243