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

cluster-launch-installer-e2e: Start setting expirationDate again #1761

Merged

Commits on Oct 4, 2018

  1. cluster-launch-installer-e2e: Start setting expirationDate again

    We'd dropped this in 3f2f01c
    (ci-operator/config/openshift/installer/master: Move to
    openshift-install, 2018-09-26, openshift#1677).  But since
    openshift/installer@98a35316 (pkg/asset/installconfig: Add
    _CI_ONLY_STAY_AWAY_OPENSHIFT_INSTALL_AWS_USER_TAGS, 2018-09-28,
    openshift/installer#364), the installer supports setting it again, so
    we can add it back.
    
    As the name suggests, this variable is not a stable API.  Soon the new
    installer will be able to load the configuration from YAML (again),
    but we can keep adjusting as the installer evolves.
    wking committed Oct 4, 2018
    Configuration menu
    Copy the full SHA
    b20d571 View commit details
    Browse the repository at this point in the history