Can you guys fix your issues tab?

[phillip-martin]

Q	A
🐛 Bug fix?	no
🚀 New feature?	no
⚠ Deprecations?	no
❌ BC Break	no
🔗 Related issues	#...
❓ Documentation	yes

Description

Your issues tab in Github is currently missing, but it is indexed in Google. Could you please add it back? We're trying to understand a particular message output by driftctl and an existing issue might be helpful. If for some reason you don't want an issues tab, could you elaborate on why and where to go for problems like these?

[CLAassistant]

All committers have signed the CLA.

[karniwl]

Hi @phillip-martin, thanks for reaching out.
The reason we disabled the issues tab is this project is now in maintenance mode. and we cannot promise to review contributions, as mentioned here.
You're welcome to share the issue you encountered here if you like, but again, unfortunately we can't promise to review it or address it.
I understand what you mean about historical issues context which may be useful, we'll look into it to see if we can find a different solution on GitHub that would answer this.
Either way, please feel free to fork the project to apply any changes you might want to make.

Apologies for the inconvenience.
Karni

[phillip-martin]

@karniwl I appreciate the reply, and I also want to mention that this piece of software has been very helpful for us. That said, I think moving into "maintenance mode" is all the more reason to include the issues tab. People who have already adopted this software into their ecosystem (which we as Snyk customers did just over a month ago - just prior to the announcement that this project is in maintenance mode) are now running blind when they run into problems because they can't see if others have experienced the same thing, and they don't have an appropriate place to ask about them. I know that it can seem like a lot of noise to have issues popping up for a project in "maintenance mode," but to be completely frank, disabling the issues tab makes it seem more like the software is in "abandon mode" rather than "maintenance mode."

If no further active development is going to happen for this tool, it would be helpful and appreciated to elaborate on why this is the case and to provide suggested alternatives.

[sundowndev]

Hi @phillip-martin, until a proper solution is found, you can still access the cached web page here.

To view cache of any webpage (if available), type on Google : cache:https://github.com/snyk/driftctl/issues/1548

[karniwl]

Hi @phillip-martin, just re-enabled the issues tab, I hope you find it useful.

As per your latter inquiry, I can share the following:
Managed drift detection capabilities or snyk iac describe --only-managed (and -- drift and --all) will be deprecated from the Snyk CLI and driftctl come July, 14, 2023 and EOL’ed on September, 30, 2023, or 90 days thereafter. We will continue to support unmanaged resource drift detection or snyk iac describe --only-unmanaged in the Snyk CLI and driftctl as a unique capability in the market.

We recommend using the terraform plan command (see Hashicorp Docs) which covers the exact same functionality as snyk iac describe --only-managed does. The ‘terraform plan’ command compares a user's local state configuration to the user's remote configuration and outputs the differences or drift events.

If you are a customer of Terraform Enterprise, there is already a tutorial on using their UI to add a layer of alerting on detected drift events as well.

[karniwl]

Closing the PR, if there's any further need, feel free to reopen