Skip to content
New issue

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

feat(pipelines): add property to specify a namespace so exported variables can be used #15964

Closed

Conversation

berenddeboer
Copy link
Contributor

The pipelines interface currently does not allow setting the namespace of an action. And no "automatic" namespaces are created.

This addition allows specifying variableNamespace on a CodeBuildStep.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@gitpod-io
Copy link

gitpod-io bot commented Aug 10, 2021

dependabot bot and others added 5 commits August 10, 2021 12:32
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 2.3.0 to 2.4.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v2.3.0...v2.4.0)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…uring tests (aws#15953)

In v1, the default value of the @aws-cdk/core:newStyleStackSynthesis flag is false. As a consequence, Template.fromStack() generates, by default, a template without the rule and parameter related to bootstrap versions. In v2, the default value of this flag is true. So this test fails in the v2 branch. By explicitly setting the flag to false, we ensure that the tests passes on both v1 and v2, regardless of the default values.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
… consistent template during tests (aws#15955)

In v1, the default value of the `@aws-cdk/core:newStyleStackSynthesis` flag is `false`. As a consequence, `Template.fromStack()` generates, by default, a template without the rule and parameter related to bootstrap versions. In v2,  the default value of this flag is `true`. So this test fails in the v2 branch. By explicitly setting the flag to `false`, we ensure that the tests passes on both v1 and v2, regardless of the default values.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…uce a consistent template during tests (aws#15960)

In v1, the default value of the `@aws-cdk/core:newStyleStackSynthesis` flag is `false`. As a consequence, `Template.fromStack()` generates, by default, a template without the rule and parameter related to bootstrap versions. In v2,  the default value of this flag is `true`. So this test fails in the v2 branch. By explicitly setting the flag to `false`, we ensure that the tests passes on both v1 and v2, regardless of the default values.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 90f3e11
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

@rix0rrr rix0rrr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why all the unrelated changes?

I'd feel more for a codeBuildStep.variable('asdf') method which creates a unique namespace and returns the corresponding '#{MyStep1481.asfd}' expression.

@berenddeboer
Copy link
Contributor Author

Unrelated changes: must have come in when I tried rebase against latest, sorry about that. I will try the update branch button here in the future.

I like your proposal: should that also insert things into the exported section of buildspec.yml? I think I've seen this approach in the code-pipelines, they seem to generate a unique namespace, at least saw that in the comments there I think. So basically the idea is to make that available in pipelines?

@rix0rrr
Copy link
Contributor

rix0rrr commented Sep 17, 2021

should that also insert things into the exported section of buildspec.yml?

Weeelll... it could, but I'm not sure we can make that SUPER easy and obvious. Better to leave the underlying CodeBuild mechanism there I think.

@igilham
Copy link
Contributor

igilham commented Dec 16, 2021

@rix0rrr Is there still an interest in pursuing this feature? I have to ask, since you closed my related PR for absolutely no reason.

@rix0rrr
Copy link
Contributor

rix0rrr commented Feb 16, 2022

#17189 is closer to what I want, so I will be finishing that one.

@rix0rrr rix0rrr closed this Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/pipelines CDK Pipelines library
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants