Skip to content

Conversation

@DocLM
Copy link

@DocLM DocLM commented Jun 6, 2024

Thank you for helping out! ✨

We really appreciate your commitment to improving Architect

To maintain a high standard of quality in our releases, before merging every pull request we ask that you've completed the following:

  • Forked the repo and created your branch from main
  • Made sure tests pass (run npm it from the repo root)
  • Expanded test coverage related to your changes:
    • Added and/or updated unit tests (if appropriate)
    • Added and/or updated integration tests (if appropriate)
  • Updated relevant documentation:
  • Summarized your changes in changelog.md
  • Linked to any related issues, PRs, etc. below that may relate to, consume, or necessitate these changes

Changes

Hello, I've updated the CDN invalidation code to handle invalidation only if CDN explicitely enabled and managed by Architect.
This should unlock the discussion in architect/architect#1483

@DocLM DocLM force-pushed the bugfix/cdn-invalidation branch from 280a5a5 to d3116f4 Compare June 6, 2024 09:49
lpsinger added a commit to lpsinger/gcn.nasa.gov that referenced this pull request Dec 6, 2024
Add patch from architect/deploy#389 to
prevent Architect from invalidating our CloudFront cache, which
would cause performance degradataion for users.
lpsinger added a commit to nasa-gcn/gcn.nasa.gov that referenced this pull request Dec 6, 2024
Add patch from architect/deploy#389 to
prevent Architect from invalidating our CloudFront cache, which
would cause performance degradataion for users.
Copy link
Member

@filmaj filmaj left a comment

Choose a reason for hiding this comment

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

This looks OK to me but trying to figure out how to get the tests to run...

@filmaj filmaj force-pushed the bugfix/cdn-invalidation branch from d3116f4 to 6bf982d Compare March 26, 2025 02:56
@lpsinger
Copy link
Contributor

lpsinger commented Apr 7, 2025

Any updates on this?

@filmaj
Copy link
Member

filmaj commented Apr 7, 2025

We should add some tests to this PR to enshrine this behaviour; I'm not sure the current state of this repo, there are probably some general updates needed, like node version targeting in github actions and so on. It also seems like many tests are commented out.. when I have a moment this week in the evenings, I'll try to take a look.

@lpsinger
Copy link
Contributor

lpsinger commented Jul 9, 2025

Any updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants