docs: update readme after oauth vars change in tests (#418)

* docs: update readme after oauth vars change in tests

* update license

* update task name

Author: artis3n

.github/workflows/molecule.yml

@@ -51,7 +51,7 @@ jobs:
       - name: Install packages
         run: poetry install --no-interaction
 
-      - name: Default scenario
+      - name: Run scenario
         run: poetry run molecule test --scenario-name "${{ inputs.scenario }}"
         env:
           MOLECULE_DISTRO: "${{ inputs.image }}"

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2021-2023 Ari Kalfus
+Copyright (c) 2021-2024 Ari Kalfus
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -362,12 +362,13 @@ and are automatically cleaned up within 30 minutes-48 hours.
 
 This value is stored in a [GitHub Action secret][] with the name `TAILSCALE_CI_KEY`.
 To test OAuth authkey compatibility, a Tailscale OAuth client secret is stored as `TAILSCALE_OAUTH_CLIENT_SECRET`.
-To test this role locally, store the Tailscale ephemeral auth key in a `TAILSCALE_CI_KEY` env var
-and, if running the `oauth` Molecule scenario,
-add an OAuth client secret in a `TAILSCALE_OAUTH_CLIENT_SECRET` env var.
 If you are a Collaborator on this repository,
 you can open a GitHub CodeSpace and these secrets will be pre-populated for you into the environment.
 
+To test this role locally, store the Tailscale ephemeral auth key in a `TAILSCALE_CI_KEY` env var
+and, if running the `oauth` Molecule scenario,
+add an OAuth client secret in a `TAILSCALE_CI_KEY` env var.
+
 Alternatively for Molecule testing,
 you can use a [Headscale][] container that is spun up as part of the create/prepare steps.
 To do this, set a `USE_HEADSCALE` env variable.