Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 24 20:30
    Travis hvac/hvac (master) passed (1502)
  • Jan 23 15:21
    Travis hvac/hvac (develop) passed (1501)
  • Jan 17 20:33
    Travis hvac/hvac (master) passed (1500)
  • Jan 16 15:20
    Travis hvac/hvac (develop) passed (1499)
  • Jan 10 20:30
    Travis hvac/hvac (master) passed (1498)
  • Jan 09 15:19
    Travis hvac/hvac (develop) passed (1497)
  • Jan 09 11:10
    Tim1000V commented #551
  • Jan 09 10:37
    Tim1000V opened #551
  • Jan 03 20:35
    Travis hvac/hvac (master) passed (1496)
  • Jan 02 15:27
    Travis hvac/hvac (develop) passed (1495)
  • Jan 01 14:32
    drewmullen commented #537
  • Jan 01 03:15
    codecov-io commented #533
  • Jan 01 03:14
    codecov-io commented #533
  • Jan 01 03:14
    codecov-io commented #533
  • Jan 01 03:13
    codecov-io commented #533
  • Jan 01 03:12
    codecov-io commented #533
  • Jan 01 03:12
    Travis hvac/hvac#533 passed (1494)
  • Jan 01 03:08
    jeffwecan commented #537
  • Jan 01 03:00
    codecov-io commented #533
  • Jan 01 03:00
    jeffwecan synchronize #533
drewmullen
@drewmullen
To https://github.com/hvac/hvac.git
 ! [remote rejected] develop -> develop (protected branch hook declined)
error: failed to push some refs to 'https://github.com/hvac/hvac.git
did you enable protection?
Jeffrey Hogan
@jeffwecan
I made no changes there
I suppose a force push hits some other setting?
drewmullen
@drewmullen
most likely
Jeffrey Hogan
@jeffwecan
toggled it off briefly, try again now?
drewmullen
@drewmullen
done
ty
sorry about that...
D:
Jeffrey Hogan
@jeffwecan
np! if it makes you feel better, I've only done that about 15 times ;P
probably should read up more on github's branch protection settings since I'm clearly missing something :shrug:
drewmullen
@drewmullen
hmm so do i have to rebase my changes against this new forced history?
*adds to long list of todos
Jeffrey Hogan
@jeffwecan
I would assume you can just reset back to your last commit on a different branch?
since you force pushed to an extant commit, I think your commits are still properly based on develop proper
drewmullen
@drewmullen
before i reset i created a new branch and pushed to my fork
ill open a pr against dev and see if it barfs
llamasoft
@llamasoft
Is there a way to force Travis tests to rerun without pushing an empty commit? I just had another test fail due to network issues: https://travis-ci.org/hvac/hvac/builds/598874415
Jeffrey Hogan
@jeffwecan
image.png
perhaps not without write access on the associated repo. I see a restart job button in the top-right there ^
llamasoft
@llamasoft
I don't have that button. :(
Jeffrey Hogan
@jeffwecan
clicking the buttons then heh
might could see if travis has any concept of retry attempts?
llamasoft
@llamasoft
Maybe, but I think retires only make sense in part of the pre-job setup steps (i.e. Vault download, pip installs). Manual retries are probably fine for right now.
Jeffrey Hogan
@jeffwecan
@llamasoft: Also, since you're here now :), I'm thinking it might be easiest to go ahead and cut a new release version before merging hvac/hvac#533 and do that over the next day or two
#533 has the potential to disrupt folks' usages in potentially unexpected way, so it may make sense to cut a patch release with your recent additions (along with some of the other low-impact PRs from the community) and then do a minor version bump for #533 to help indicate the chance we're introducing breaking changes
also, as a metapoint, I've been incredibly pleased to see you tackle some long lingering issues with aplomb and if you have in interest in helping maintain this module let me know! i.e., if you're interested in having write access and helping review other folks' PRs, etc.
drewmullen
@drewmullen
Alright! “conference heck” is now over… im back! went to 5 conferences in 2 months and a few other travels in between. feels like ive been gone for a while!
my god @llamasoft you have been crushing it lol thanks for the contributions and thoughtful explanations
Viacheslav Vasilyev
@avoidik
hi guys, how to use iam_login?
vault_client = hvac.Client(url=vault_addr)
what's next?
start here
i hvaent personally used it but thats the doc
Viacheslav Vasilyev
@avoidik
I see it, but it is absolutely not obvious how to inherit this method from the instantiated client?
nvm
vault_client.auth.aws.iam_login()
thanks anyway ;)
Viacheslav Vasilyev
@avoidik
client.auth_aws_iam will be deprecated soon btw
drewmullen
@drewmullen
yeah looks like that doc needs to be updated to point to the new auth.aws.x module
feel free to open a ticket on that
rightblank
@rightblank
Hi, everyone, met a problem here, need you r help
I run the following to login to the vault but get permission denied when accessing the secrets
client = hvac.Client(url='https://<IP>:8200',namespace='NAMESPACE', verify='path_to_ca.crt')
client.auth_approle(<role_id>, <secret_id>)
the auth_approle return seems alright, I can use the token it returned to login on cli.
the way I get the secrets client.secrets.kv.v2.read_secret_version(<path-to-secret>)
rightblank
@rightblank
Never mind, guys, I figured it out that I put the mount_point into the path when read secret.
Jeffrey Hogan
@jeffwecan
FYI going to finally get around to cutting a release today :)