github.com/redhat-appstudio/e2e-tests@v0.0.0-20240520140907-9709f6f59323/default.env (about)

     1  # A github token used to create AppStudio applications in github.
     2  # Required: yes
     3  export GITHUB_TOKEN=''
     4  
     5  # A quay token to push components images to quay.io.
     6  # Note: The quay token must be your dockerconfigjson encoded in base64 format. It is generated when you run `docker login quay.io` (or `podman login quay.io`).
     7  # Example: export QUAY_TOKEN=$(base64 < ~/.docker/config.json)
     8  # Required: yes
     9  export QUAY_TOKEN=''
    10  
    11  # A quay organization where repositories for component images will be created.
    12  # Required: yes
    13  export DEFAULT_QUAY_ORG=''
    14  
    15  # A quay token of OAuth application for DEFAULT_QUAY_ORG with scopes -  Administer organizations, Administer repositories, Create repositories 
    16  # Required: yes
    17  export DEFAULT_QUAY_ORG_TOKEN=''
    18  
    19  # GitHub organization where Red Hat AppStudio applications will be created and pushed.
    20  # Note: It must be an organization (which can be created for free), and cannot be your regular GitHub account.
    21  # Example: redhat-appstudio-qe
    22  # Required: no (recommended)
    23  export MY_GITHUB_ORG=''
    24  
    25  # Quay organization/account where to push components containers.
    26  # It is recommended to create your own account.
    27  # Example: redhat-appstudio-qe
    28  # Required: no (recommended)
    29  export QUAY_E2E_ORGANIZATION=''
    30  
    31  # Name of the namespace used for running build-templates E2E tests.
    32  # Required: no
    33  export E2E_APPLICATIONS_NAMESPACE=''
    34  
    35  # The name of the private git repository used in HAS E2E tests.
    36  # Your GITHUB_TOKEN should be able to read from it.
    37  # Example: https://github.com/redhat-appstudio-qe/private-quarkus-devfile-sample
    38  # Required: no
    39  export PRIVATE_DEVFILE_SAMPLE=''
    40  
    41  # A valid quay robot account username to make quay oauth.
    42  # Required: no
    43  export QUAY_OAUTH_USER=''
    44  
    45  # A valid quay quay robot account token to make oauth against quay.io.
    46  # Required: no
    47  export QUAY_OAUTH_TOKEN=''
    48  
    49  # A valid docker.io token to avoid pull limits.
    50  # Format: username:access_token.
    51  # Example: susdas:43228532-b374-11ec-989b-98fa9b70b97d
    52  # Required: no
    53  export DOCKER_IO_AUTH=''
    54  
    55  # A specific github organization from where to download infra-deployments repository.
    56  # Example: redhat-appstudio
    57  # Required: no
    58  export INFRA_DEPLOYMENTS_ORG=''
    59  
    60  # A valid infra-deployments branch.
    61  # Example: main
    62  # Required: no
    63  export INFRA_DEPLOYMENTS_BRANCH=''
    64  
    65  # Run only test suites with the given Giknkgo label.
    66  # Required: no
    67  export E2E_TEST_SUITE_LABEL=''
    68  
    69  # Level of verbosity for klog.
    70  # Required: no
    71  export KLOG_VERBOSITY='1'
    72  
    73  # Expiration for tags created by pull-request pipelineruns.
    74  # Format: digits + h (hours), d (days) or w (weeks)
    75  # Example: 5d
    76  # Required: no
    77  export IMAGE_TAG_EXPIRATION='6h'
    78  
    79  # A github appid used to set up Pac integerating with Github App
    80  # Note: how to get Github App ID https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/authenticating-as-a-github-app-installation#using-octokitjs-to-authenticate-with-an-installation-id
    81  # Required: only for running tests that are using PaC (see README.md for more details)
    82  export E2E_PAC_GITHUB_APP_ID=''
    83  
    84  # A github private key in base64 format used to set up Pac integerating with Github App
    85  # Note: How to get private key https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/managing-private-keys-for-github-apps
    86  # Required: only for running tests that are using PaC (see README.md for more details)
    87  export E2E_PAC_GITHUB_APP_PRIVATE_KEY=''
    88  
    89  # Only for upgrade tests
    90  # Branch with changes for upgrade (eg. new image tag...)
    91  # Example: quality-dashboard
    92  # Required: yes (for upgrade tests)
    93  export UPGRADE_BRANCH=quality-dashboard
    94  
    95  # Only for upgrade tests
    96  # Branch with changes for upgrade (eg. new image tag...)
    97  # Example: redhat-appstudio-qe
    98  # Required: no
    99  # Default value(if not specified): redhat-appstudio
   100  export UPGRADE_FORK_ORGANIZATION=redhat-appstudio-qe
   101  
   102  # Setting this env var to "true" makes rhtap-demo test scenario to skip cleanup.
   103  # Implemented as part of https://issues.redhat.com/browse/RHTAPBUGS-890
   104  # export E2E_SKIP_CLEANUP=true
   105  
   106  # By default the e2e-tests installer configures master nodes as schedulable.
   107  # However this option is not recommended for use in production (https://access.redhat.com/solutions/4564851)
   108  # Set the following env var's value to "false" if you don't want user workloads being scheduled on master/control plane nodes of your cluster.
   109  export ENABLE_SCHEDULING_ON_MASTER_NODES=true