8000 **DO NOT MERGE** codegen results after ci-mgmt upgrade by ctreatma · Pull Request #353 · equinix/pulumi-equinix · GitHub
[go: up one dir, main page]
Skip to content

**DO NOT MERGE** codegen results after ci-mgmt upgrade - #353

Closed
ctreatma wants to merge 10 commits into
mainfrom
pulumi-ci-mgmt-generated-code
Closed

**DO NOT MERGE** codegen results after ci-mgmt upgrade#353
ctreatma wants to merge 10 commits into
mainfrom
pulumi-ci-mgmt-generated-code

Conversation

@ctreatma
@ctreatma ctreatma commented Sep 23, 2026 •
edited
Loading
Copy link
Copy Markdown
Contributor

The contents of this PR may end up being rolled into #350. For now they are separate so that it's easier to focus on codegen changes here and focus on workflow/scaffolding changes in #350.

@github-actions
github-actions Bot commented Sep 23, 2026 •
edited
Loading
Copy link
Copy Markdown

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "**DO NOT MERGE** codegen results after ci-mgmt upgrade". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@ctreatma ctreatma changed the title Pulumi ci mgmt generated code **DO NOT MERGE** codegen results after ci-mgmt upgrade Sep 23, 2026
@github-actions
github-actions Bot commented Sep 23, 2026
Copy link
Copy Markdown

Does the PR have any schema changes?

Looking good! No breaking changes found.

New functions:

  • pulumi.providers.equinix/terraformConfig

Maintainer note: consult the runbook for dealing with any breaking changes.

@apiiro
apiiro Bot commented Sep 23, 2026
Copy link
Copy Markdown

WORKFLOW-25 · Pull Request Comments for Secrets Scanning

Workflows: "WORKFLOW-25 · Pull Request Comments for Secrets Scanning"
Policies: "Exposed Secrets with Unknown Validity in Public, Applicative Code - High"

⚠️ Apiiro found 1 new risk - 1 high ⚠️

🔴 High: Exposed Secrets with Unknown Validity in Public, Applicative Code - High in secret of type User password

  • Secret type: User password (Generic)
  • Validity: No validator
  • Exposure: Exposed
  • File type: Source Code
  • Appearances: Appears 1 time in the file
  • Preview: /// Password = "•••••", line 165
  • Insights: Public repository

Repository: pulumi-equinix
Applications: ORG - EQUINIX,PROJ: PUBLIC-OPENSOURCE (Auto)

View in Apiiro

@ctreatma
ctreatma force-pushed the pulumi-ci-mgmt-generated-code branch 3 times, most recently from 7bbe84d to dcfac38 Compare September 30, 2026 17:15
@ctreatma
ctreatma force-pushed the pulumi-ci-mgmt-generated-code branch from dcfac38 to ef33277 Compare September 30, 2026 19:22
@ctreatma
ctreatma commented Sep 30, 2026
Copy link
Copy Markdown
Contributor Author

Collapsing into #350 so that we can ensure that CI fully passes before merging the toolchain upgrade.

@ctreatma ctreatma closed this Sep 30, 2026
@ctreatma
ctreatma deleted the pulumi-ci-mgmt-generated-code branch September 30, 2026 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@ctreatma
0