Skip to content

Restore pxc Jenkins plugin baseline lost in CFN to TF migration#245

Open
nogueiraanderson wants to merge 1 commit into
mainfrom
fix-pxc-restore-plugins-groovy
Open

Restore pxc Jenkins plugin baseline lost in CFN to TF migration#245
nogueiraanderson wants to merge 1 commit into
mainfrom
fix-pxc-restore-plugins-groovy

Conversation

@nogueiraanderson

@nogueiraanderson nogueiraanderson commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Bug

  • The pxc CFN boot script fetched an init.groovy.d/plugins.groovy baseline that reinstalls pxc's plugin set on a fresh home. The CFN to TF migration carried this over for psmdb but not pxc, so a fresh-EBS rebuild of pxc comes up without it.

Fix

  • Add resources/jenkins-masters/pxc/init.groovy.d/plugins.groovy (mirrors psmdb), so the module uploads it to pxc's init-config bucket and the master fetches it at boot and on the SSM sync.
  • Reconcile the list against the live master: the retired warnings plugin is replaced by warnings-ng. All entries are already installed, so the hook is a no-op in steady state.

Notes

  • aws_instance ignores user_data, so apply only adds the S3 object and bumps the launch template. Live pxc receives the file via the init_groovy_sync SSM association. A fresh-EBS rebuild fetches it at boot.

Related

  • PR #239 (psmdb sibling, same migration regression class)

…n CFN->TF migration

- Add resources/jenkins-masters/pxc/init.groovy.d/plugins.groovy (mirrors psmdb's) so the module uploads it to pxc's init-config bucket and the master fetches it at boot and via the init_groovy_sync SSM association.
- Reconcile the plugin list against the live master: replace the retired warnings plugin with warnings-ng.
- Self-heals a fresh-EBS rebuild. No-op in steady state (plugins already installed).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant