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

FTDCS-196 - Added default panic guide for Fastly key expiration check #191

Merged
merged 5 commits into from
Jun 22, 2022

Conversation

JSRedondo
Copy link
Contributor

The panic guide is the same for any fastly key, so there is no point to repeat the same in each configuration health check.
Anyway, there is the option to set a custom panic guide, just in case.

@JSRedondo JSRedondo requested a review from a team June 21, 2022 15:52
@JSRedondo JSRedondo requested a review from a team as a code owner June 21, 2022 15:52
@@ -14,6 +15,7 @@ class FastlyKeyExpirationCheck extends Check {
constructor(options) {
super(options);
this.fastlyKey = options.fastlyKey;
this.panicGuide options.panicGuide || defaultPanicGuide;
Copy link
Member

Choose a reason for hiding this comment

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

I think just missing an equals here: this.panicGuide =

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, I realized last moments of the work shift I was faster than lucid 🤣

Copy link
Member

@alexmuller alexmuller left a comment

Choose a reason for hiding this comment

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

Looks great! For the panic guide I would say that we don't need people to contact Fastly for that. Instead we could have a message like this:

Generate a new key in your own Fastly account with the same permissions and update it in Vault or your app

@JSRedondo JSRedondo merged commit e2e6fe5 into main Jun 22, 2022
@JSRedondo JSRedondo deleted the default-panic-guide branch June 22, 2022 10:22
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.

None yet

2 participants