Sha256: e25d351c62b1d791cd69177c5e2e13bd33216511bf4da13f0aaaf044b753aa14

Contents?: true

Size: 967 Bytes

Versions: 7

Compression:

Stored size: 967 Bytes

Contents

Feature: Test the existence of a resource

  Scenario: Existing resources can be detected
    Given I load the policy:
    """
    - !resource
      kind: food
      id: bacon
    """
    And I reset the command list
    When I successfully run `conjur resource exists food:bacon`
    Then the stdout should contain exactly "true"

  Scenario: Non-existent resources are reported as such
    When I successfully run `conjur resource exists food:bacon`
    Then the stdout should contain exactly "false"
  
  Scenario: Even foreign user can check existence of a resource 
    Given I load the policy:
    """
    - &resources
      - !resource
        kind: food
        id: bacon

    - !user alice

    - !permit
      role: !user alice
      privileges:
        - read
      resources: *resources
    """
    And I login as "alice"
    And I reset the command list
    And I run `conjur resource exists food:bacon`
    Then the stdout should contain exactly "true"

Version data entries

7 entries across 7 versions & 1 rubygems

Version Path
conjur-cli-6.2.6 features/authorization/resource/exists.feature
conjur-cli-6.2.5 features/authorization/resource/exists.feature
conjur-cli-6.2.4 features/authorization/resource/exists.feature
conjur-cli-6.2.3 features/authorization/resource/exists.feature
conjur-cli-6.2.2 features/authorization/resource/exists.feature
conjur-cli-6.2.1 features/authorization/resource/exists.feature
conjur-cli-6.2.0 features/authorization/resource/exists.feature