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

fix(ecy): configuration file path changed #2

Merged
merged 1 commit into from
Jul 24, 2024
Merged

fix(ecy): configuration file path changed #2

merged 1 commit into from
Jul 24, 2024

Conversation

gforien
Copy link
Owner

@gforien gforien commented Jul 24, 2024

Using eza instead of exa
ogham/exa#1243

@gforien gforien merged commit 14750d0 into main Jul 24, 2024
@gforien gforien deleted the fix/eza branch July 24, 2024 04:49
gforien pushed a commit that referenced this pull request Oct 25, 2024
Bug: given only 1 IP in the SG, 1 is revoked, 1 is authorized

Given one IP in the SG '92.143.36.217'
Run `gf aws inboundIp`
Result: the SG now contains one IP '2a01:cb14:1686::'
Expected result:
  the SG contains both IPs '2a01:cb14:1686::', and '92.143.36.217'

Why ?
  - IPv4 is skipped, because it belongs to the SG
  - IPv6 is added to the group
  - all rules are revoked
  - the group is authorized

Fix #1:
  Revoke and authorize the whole group.
  But now the group is revoked+authorized even to the identical

Fix #2:
  Add comparison methods for []IpRange []Ipv6Range []IpPermission
  Add tests
gforien pushed a commit that referenced this pull request Oct 25, 2024
Bug: given only 1 IP in the SG, 1 is revoked, 1 is authorized

Given one IP in the SG '92.143.36.217'
Run `gf aws inboundIp`
Result: the SG now contains one IP '2a01:cb14:1686::'
Expected result:
  the SG contains both IPs '2a01:cb14:1686::', and '92.143.36.217'

Why ?
  - IPv4 is skipped, because it belongs to the SG
  - IPv6 is added to the group
  - all rules are revoked
  - the group is authorized

Fix #1:
  Revoke and authorize the whole group.
  But now the group is revoked+authorized even to the identical

Fix #2:
  Add comparison methods for []IpRange []Ipv6Range []IpPermission
  Remove methods Ip.ToAwsIpPerms() and Ip.ExistsInAwsSg()
  Add tests
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.

1 participant