question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Auto Remove Existing SECRETS and add only the new

See original GitHub issue

I recently started using this action to my certain SECRETS available to repos.

but then i found out that this action does not remove Existing SECRETS

Let me give you an example

I have configured my workflow like below

      - name: "🔄 Sync Twitter Logins"
        uses: google/secrets-sync-action@v1.4.1
        with:
          repositories_list_regex: false
          SECRETS: |
            ^TWITTER_
          REPOSITORIES: ${{ env.TWITTER_LOGINS_REPOS }}
          DRY_RUN: ${{ env.DRY_RUN }}
          CONCURRENCY: ${{ env.CONCURRENCY }}
          GITHUB_TOKEN: ${{ secrets.GH_PUBLIC_PRIVATE_TOKEN }}

and i have below EVN’s configured

env:
  DRY_RUN: false
  CONCURRENCY: 50
  TWITTER_API_KEY: ${{ secrets.TWITTER_API_KEY }}
  TWITTER_API_SECRET_KEY: ${{ secrets.TWITTER_API_SECRET_KEY }}
  TWITTER_ACCESS_TOKEN: ${{ secrets.TWITTER_ACCESS_TOKEN }}
  TWITTER_ACCESS_TOKEN_SECRET: ${{ secrets.TWITTER_ACCESS_TOKEN_SECRET }}
  TWITTER_LOGINS_REPOS: |
    varunsridharan/****
    varunsridharan/****
    varunsridharan/****
    varunsridharan/****
    varunsridharan/****

And when i ran the action to syn ll the SECRETS it also added TWITTER_LOGINS_REPOS to the repo

https://s2.do-spaces.com/2020/Jun/29/1593409947-114.jpg

I know its my mistake i should have configured the Regex Properly …

but i would be great if this action and force remove all the matching SECRETS and add only the new matched SECRETS !

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
jpoehneltcommented, Jul 7, 2020

There is no delete mechanism.

1reaction
mastermind369commented, Jul 1, 2020
Read more comments on GitHub >

github_iconTop Results From Across the Web

Modify an AWS Secrets Manager secret
To update the secret value, in the Secret value section, choose Retrieve secret value and then choose Edit. Secrets Manager creates a new...
Read more >
update-secret — AWS CLI 2.3.2 Command Reference
Secrets Manager removes outdated versions when there are more than 100, ... To add only a new version to an existing secret, use...
Read more >
Secrets | Kubernetes
You can edit an existing Secret unless it is immutable. ... However, this method creates a new Secret object with the edited data....
Read more >
Replace an expiring client secret in a SharePoint Add-in
We recommend to only remove secrets a minimum of 7 days after expiration, provided you have removed them from the application configuration.
Read more >
bitnami-labs/sealed-secrets: A Kubernetes controller ... - GitHub
The SealedSecret controller and the associated workflow are designed to keep old sealing keys around and periodically add new ones. You should not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found