forked from ekristen/aws-nuke
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Oreilly main rebase [DRAFT] #2
Draft
corybekk
wants to merge
698
commits into
oreilly-main
Choose a base branch
from
oreilly-main-rebase
base: oreilly-main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…make ready for tests
… vs account devices
* feat(iam): add createdate for access keys * feat(iam): add createdate for access keys * feat(iam): add createdate to iam user
… dir to prevent aws-nuke from breaking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I wanted to use our original oreilly/aws-nuke fork, but found that we would lack write permissions on ekristen/aws-nuke because we aren't forked from it. I created this fork
aws-nuke-v2
which will eventually be renamed toaws-nuke
once we replace the old one.I attempted to rebase
oreilly/aws-nuke
ontoekristen/aws-nuke
(see below steps) with a few goals in mind.I am not sure if this is the best approach. I have reached out to the team to discuss our path forward. Here is the slack thread.
EDIT: We have decided to just start from scratch instead of rebasing. My findings show that a lot our modules were rewritten to follow a new structure and, as a result, most, if not all, of our changes were stomped on.
Git steps
Step 1: Create a carbon copy of the current main branch in aws-nuke-v2
git checkout -b oreilly-main
Step 2: Add the remote repository for the old fork
git remote add old-fork https://github.com/oreillymedia/aws-nuke.git
git fetch old-fork
Step 3: Rebase changes from oreillymedia/aws-nuke's oreilly-main branch onto aws-nuke-v2:oreilly-main
Use the -Xours strategy to prioritize aws-nuke-v2:oreilly-main changes in conflicts
git rebase -Xours old-fork/oreilly-main
Step4: Manually fix any merge issues, delete old files, fix Go linting and static analysis errors.
Required Code Changes (not an extensive list)
Required config.yml changes
settings
.includes
account-blocklist
toblocklist
control-tower
toalternatives
issues
CLI changes
run aws-nuke
--force
and--force-sleep
we will now use --no-prompt and --prompt-delayTesting
cl-cloud-user-creator
.