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

Change admin container logic to use public keys from user-data #19

Merged
merged 4 commits into from
Feb 24, 2021

Commits on Feb 18, 2021

  1. Add jq to installed packages

    jpculp committed Feb 18, 2021
    Configuration menu
    Copy the full SHA
    95d773e View commit details
    Browse the repository at this point in the history

Commits on Feb 24, 2021

  1. Replace IMDS logic with fetching public keys from user-data

    This change allows the admin container to be platform agnostic as it
    retrieves its .ssh/authorized_keys from a base64-encoded JSON block in
    user-data rather than relying on the AWS instance metadata service
    (IMDS) directly.
    
    Example JSON: {"ssh":{"authorized_keys":[]}}
    jpculp committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    9e534bd View commit details
    Browse the repository at this point in the history
  2. Add support for TrustedUserCAKeys

    This allows users who want to set TrustedUserCAKeys to do so by adding
    them as a base64-encoded JSON block in user-data.
    
    Example JSON: {"ssh":{"trusted_user_ca_keys":[]}}
    jpculp committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    e8d90e3 View commit details
    Browse the repository at this point in the history
  3. Release v0.6.0

    This commit bumps the version from v0.5.2 to v0.6.0 and adds a changelog
    for the admin container.
    jpculp committed Feb 24, 2021
    Configuration menu
    Copy the full SHA
    14064c0 View commit details
    Browse the repository at this point in the history