Skip to content

Commit 6f883d0

Browse files
Update content/blog/using-the-hpegl-hpe-greenlake-and-morpheus-terraform-providers-in-concert-to-create-provision-and-manage-hpe-pce-private-cloud-enterprise-vmaas-instances.md
Co-authored-by: liam-m-carolan <[email protected]>
1 parent 747bffd commit 6f883d0

1 file changed

+3
-3
lines changed

content/blog/using-the-hpegl-hpe-greenlake-and-morpheus-terraform-providers-in-concert-to-create-provision-and-manage-hpe-pce-private-cloud-enterprise-vmaas-instances.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,9 @@ These two providers complement each other: 
3737

3838
The glue between these two providers is a hpegl *Data Source* called *hpegl_vmaas_morpheus_details*.  For a specific VMaaS *location* this data source will output: 
3939

40-
* A Morpheus Access Token 
41-
* The URL of the Morpheus instance 
42-
* The time to expiry of the Access Token (in seconds) 
40+
* A Morpheus access token. 
41+
* The URL of the Morpheus instance. 
42+
* The time to expiry of the access token (in seconds). 
4343

4444
The first two outputs can then be passed into a Morpheus provider stanza. See the following example where there is just one *location* for a VMaaS instance:
4545

0 commit comments

Comments
 (0)