Skip to content

fix: untangle dependency between PatchManager and PgstacInfra stacks#85

Merged
hrodmn merged 7 commits intomainfrom
fix/patch-manager-dependency
Mar 12, 2026
Merged

fix: untangle dependency between PatchManager and PgstacInfra stacks#85
hrodmn merged 7 commits intomainfrom
fix/patch-manager-dependency

Conversation

@hrodmn
Copy link
Collaborator

@hrodmn hrodmn commented Mar 12, 2026

I think I created this snarl by suggesting we pipe the instance ids from PgstacInfra into the PatchManger construct 😞

It will require manually deleting the PatchManager stacks to break the dependency that is blocking updates to the PgstacInfra stacks.

adds some deployment stability magic
@jjfrench
Copy link
Member

Is this because the instance ids are changing and this breaks the patch manager? does this behavior also need to change in eoapi-cdk then?

@hrodmn
Copy link
Collaborator Author

hrodmn commented Mar 12, 2026

Is this because the instance ids are changing and this breaks the patch manager? does this behavior also need to change in eoapi-cdk then?

I think it is specific to maap-eoapi since we deploy the patch manager in a separate Stack? In eoapi-cdk it should be ok since the patch manager is contained within the PgstacDatabase construct.

@jjfrench
Copy link
Member

Do you want to keep it as the instance ID's then? The SSM param route would also work with the instance names if you wanted it change less - also looks fine as is

@hrodmn
Copy link
Collaborator Author

hrodmn commented Mar 12, 2026

@jjfrench I think I'll leave it as-is for now, I upgraded the eoapi-cdk version to 11.3.0 to catch the pgbouncer ami fix too so hopefully we get fewer resource changes in our future deployments!

@hrodmn hrodmn deployed to synthtest March 12, 2026 21:29 — with GitHub Actions Active
@hrodmn hrodmn merged commit 76d1937 into main Mar 12, 2026
2 checks passed
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.

2 participants