Most reactive charms react on identity-service.available but the
current interface distinguishes between available and available.auth. It
is somewhat assumed by most charms that identity-service.available is
equivalent to identity-service.available.auth, as what charms are
concerned with is the ability to authenticate against the cloud.
Collapse the difference between identity-service.available and
identity-service.available.auth.
Continue to set identity-service.available.auth for any charms that may
rely on it.
Reviewed: https:/ /review. opendev. org/741547 /git.openstack. org/cgit/ openstack/ charm-interface -keystone/ commit/ ?id=a48a1e826ac 0a74ab05a16c441 cda4e4b34b1241
Committed: https:/
Submitter: Zuul
Branch: master
commit a48a1e826ac0a74 ab05a16c441cda4 e4b34b1241
Author: David Ames <email address hidden>
Date: Thu Jul 16 14:14:44 2020 -0700
Collapse available and available.auth
Most reactive charms react on identity- service. available but the service. available is service. available. auth, as what charms are
current interface distinguishes between available and available.auth. It
is somewhat assumed by most charms that identity-
equivalent to identity-
concerned with is the ability to authenticate against the cloud.
Collapse the difference between identity- service. available and service. available. auth.
identity-
Continue to set identity- service. available. auth for any charms that may
rely on it.
Change-Id: I494feea5f3ef87 06140ce712b1e02 5e52b0dfbd1
Closes-Bug: #1818113